Prerequisites for the Nodinite Mule ESB Logging agent
Unlock seamless integration and powerful monitoring by preparing your environment for the Nodinite Mule ESB Logging Agent. This guide covers everything you need for a successful installation and operation.
We recommend installing this agent close to your Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server).
Software Requirements
The Mule ESB Logging Agent is a Windows Service and is usually installed on the Nodinite application server.
| Product | |
|---|---|
| Windows Server | Windows 2025 Windows 2022 Windows 2019 Windows 2016 Windows 2012 R2 Windows 2012 |
| .NET Framework | .NET Framework 4.5 or later |
Supported Versions
Cloud technologies evolve rapidly, and MuleSoft deprecates older API versions regularly. Nodinite always supports the APIs supported by MuleSoft. Update Nodinite and the Mule ESB Logging Agent as needed to stay current.
Subscribe to our Release Notes to stay informed about updates.
What folder rights does the Mule ESB Logging Agent require?
If you use Mule ESB on-premise with the Log4J file appender, logged events are created on local disk or a Windows File share (SMB).
The Mule ESB Logging Agent must have Read, Write, and Change permissions to consume these events.
What Anypoint Cloudhub rights does the Mule ESB Logging Agent require?
- The agent uses the MuleSoft Anypoint Cloudhub API to read logged events with tracked properties. Grant the agent the necessary access rights as described in the Configuration.
What Windows User Rights does the Mule ESB Logging Agent require?
The agent is installed as a Windows Service, usually on the Nodinite application server. Virtual machines are supported.
- Use a local named account or domain account (preferred).
- Access and run-time rights:
- Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.
What Firewall settings are required for the Mule ESB Logging Agent?
The Mule ESB Logging Agent requires both inbound and outbound communication:
- Between the Mule ESB Logging Agent and SMB File share or folder
- Between the Mule ESB Logging Agent and Cloudhub API
- Between the Mule ESB Logging Agent and the Log API
1. Between the Mule ESB Logging Agent and SMB File share or folder
The Mule ESB Logging Agent uses the SMB protocol to access the remote file share.
The following TCP ports must be open:
| Port | Name | Inbound | Outbound | TCP | UDP | Comment |
|---|---|---|---|---|---|---|
| 53 | DNS | The Agent needs to know where your other servers/services are (can sometimes be solved with user-defined entries in the hosts file in each Windows server instance). See Microsoft's DNS guide. |
||||
| 135-139 | SMB | Microsoft file sharing SMB | ||||
| 445 | SMB | Direct-hosted SMB traffic |
For full documentation, visit [SMB: File and printer sharing ports should be open][FilePorts] and Internet firewalls can prevent browsing and file sharing .
2. Between the Mule ESB Logging Agent and Cloudhub API
| Port | Name | Inbound | Outbound | TCP | UDP | Comment |
|---|---|---|---|---|---|---|
| 443 | HTTPS | Secure outbound traffic with the Cloudhub API |
3. Between the Mule ESB Logging Agent and the Log API
When logging is enabled, the Mule ESB Logging Agent requires one of the following outbound TCP ports to be open to access the Log API (configurable):
| Port | Name | Inbound | Outbound | TCP | UDP | Comment |
|---|---|---|---|---|---|---|
| 80 | HTTP | Default for HTTP | ||||
| 443 | HTTPS | Default for HTTPS |
Note
If the Mule ESB Logging Agent and the Log API are on the same server, use HTTP for best performance and security.
Frequently asked questions
Find solutions to common problems and FAQs for the Nodinite Mule ESB Logging Agent in the Troubleshooting user guide.
About Mule ESB
- Anypoint Studio 6 requires Java8
Next Step
Add or manage a Monitoring Agent Configuration
Install the Mule ESB Logging Agent